Enersight Batch Import
On the Enersight Batch Import screen, you need to set up one or more batches and specify the import settings.
Set up the import batches
Each tab corresponds to an import batch. Batches can be used to load data from several source locations at once, or to load data from the same source with different settings. Each batch is processed completely before the data loader moves on to the next batch; processing proceeds from left to right. The general batch management buttons are described in the table below (the same functions are available in the context menu if you right-click a batch tab).
Note: The import begins with projects at the left-most batch tab and proceeds from left to right. Each batch is processed completely before the data loader moves on to the next batch.
Button | Description |
---|---|
Creates a new batch. | |
Renames the selected batch. | |
Deletes the selected batch. | |
Moves the selected batch to the left. | |
Moves the selected batch to the right. |
Enersight settings
The settings are described in the table below.
Note that if you see any incorrect responses when modifying the Enersight connection (e.g., not able to connect to the server), then try closing the loader completely and re-opening.
Setting | Description |
---|---|
Enersight connection | Select the Enersight server connection to be used. Connections are managed in the Dataflow Configuration workspace (see Enersight Connections). Note that every connection has its own workgroup-based access control. |
Enersight profile | Select from the list of profiles that has been found in the Enersight server, for the User account set by the chosen Enersight connection. Profiles are created in Enersight to define how data will be exported (selection and grouping of variables, result data sets, etc.). See Enersight export settings. |
Document path | The document path determines how documents will be found in the Dataflow hierarchy. The path is built up by selecting a sequence of attributes in the Configure Document Path dialog (the necessary attributes for the different batch configurations must have been defined as User Data string variables in Enersight). The document path might be something like 'Country\Region\Field\Well'. |
Opportunity filter | Specifies a filter to be applied to the Enersight opportunity data (default is no filter). |
Scenario mappings
These settings define the mapping of outcomes in Enersight to Dataflow scenarios for imported documents. The outcomes found in the Enersight profile will be listed in a table. Each outcome will be mapped to a scenario based on a specified scenario tag, or a scenario name, as explained below.
Option | Description |
---|---|
Import into tagged scenario | Select this option to import data into a scenario with a particular tag. For each Enersight Outcome, select a tag from the dropdown list of active scenario tags in Dataflow. |
Import into named scenario |
Select this option to import data into a scenario with a particular name. For each Enersight Outcome, type a scenario name in the Dataflow Scenario field. For version 16.5 Update 17 and later: When the Import into named scenario radio button is clicked, the names table will be automatically filled-in so that all the Dataflow Scenario names match the Enersight outcomes. The Dataflow names can then be edited as required. |
Create scenario if it does not exist | If you are using the Import into tagged scenario option, check this box to create a new scenario and apply the selected tag to it. If you are using the Import into named scenario option, check this box to create a new scenario with the specified name, if it does not exist. |
Create and/or apply scenario tag from named scenario | [Only for version 16.5 Update 17 and later] When Import into named scenario is selected, check this box to automatically create and/or apply a scenario tag with the same name as the document scenario. To create a new tag, the user must be granted the role 'Dataflow/Tags'; permissions on the new tag will be Full Access for the current user (if the tag name fails required validation rules, it won't be created and a warning will be recorded in the log). If the tag already exists, it can only be applied if the current user has 'Update, Apply & Remove' permission granted for the tag (if not, the tag isn't applied and a warning will be recorded in the log). |
Change Record settings
Imported data will be saved in the destination Dataflow documents as a new revision. Specify Change Record information in the same way as you would provide when editing documents in Dataflow.
Batch Settings management
You can store batch import settings for reuse later. To open a stored configuration, select it from the list in the Batch import settings field at the top of the screen. Next to this field is a drop-down menu with settings management options, which are explained in the table below. You can export a stored configuration to a 'XET' file in the local file system, and import configurations from XET files (you can use this feature to move configurations between different PlanningSpace tenants, for example).
Option | Description |
---|---|
New Settings | Creates a new stored configuration. |
Save Settings | Saves the current on-screen settings into the currently-selected configuration. |
Rename Settings | Renames the selected stored configuration. |
Delete Settings | Deletes the selected stored configuration. |
Import Settings | Import a settings configuration from a local file (XET format). |
Export Settings | Export a settings configuration to a local file (XET format). |
View All Settings | (only for the Economics and Financials loaders) This contains the utilities Export to CSV to export settings into a CSV file, and Copy Settings Between Batches to optionally copy settings values between batch tabs. |